Network interface for tracking radio resource utilization

ABSTRACT

A method is provided for performing RAN-usage-based tracking in a wireless core network. The method includes receiving a connection authorization request from a radio access network (RAN); obtaining a plan code for a communication device associated with the connection authorization request; associating, based on the plan code, the communication device with a RAN-usage-based plan; and sending, in response to the associating, tracking instances of RAN usage by the communication device to a usage-tracking server device.

BACKGROUND

Internet of Things (IoT) technology refers to a wide range of devicesthat can collect and forward data. The IoT devices may be configured totransfer the data via a cellular network. Since IoT technology hasnearly limitless applications that can be leveraged to form new anduseful services, interest among service providers and developers in IoTtechnology continues to increase. Supporting the growing number ofconnection requests and volume of data from IoT technology presents asignificant challenge for providers of network services. Particularly,many IoT communications are characterized by infrequent, small-datatransactions. While IoT devices individually may constitute a small loadon the network, the overall effect of these devices can burden networkresources.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an exemplary network environmentaccording to an implementation described herein;

FIG. 2 is a diagram illustrating exemplary components of a device thatmay be included in a device of FIG. 1;

FIG. 3 is a diagram illustrating exemplary logical components of theaccess and mobility management function (AMF) of FIG. 1;

FIGS. 4A and 4B are diagrams illustrating exemplary logical componentsof the usage-tracking server of FIG. 1;

FIG. 5 is an exemplary signal flow diagram for logging radio resourceuse according to an implementation described herein;

FIGS. 6A and 6B are exemplary signal flow diagrams for controlling userequipment (UE) behavior based on radio resource use, according toimplementations described herein;

FIG. 7 is a flowchart of a process for tracking radio resourceutilization according to an implementation described herein; and

FIG. 8 is a diagram illustrating use cases according to animplementation described herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

Today, mobile service plans are commonly track data usage by a device(e.g., a 2 GB, 5 GB, or “unlimited” monthly data plan). These models donot correlate well to IoT communications that usually initiate periodicnetwork connections with nominal data usage. IoT customers in thedata-based plans may be accountable for unnecessary data, while serviceproviders have to support a disproportionate amount of small datasessions.

Standards for future wireless core networks, including Third GenerationPartnership Project (3GPP) 5G network standards, are being developed tosupport new data use cases. One area of future standards developmentincludes optimized connectivity for sporadic data transmissions, such asdata transmissions characterized by IoT communications (also referred toas machine-type communications). As these standards are being developed,architectural changes may be put in place to supportradio-connectivity-based tracking in wireless core networks.

Systems and methods described herein provide systems suitable foroperators to monitor and control IoT devices. Network architecture andinterfaces are provided to enable tracking customer network use based onper-device radio resource utilization, irrespective of data usage. Forexample, depending on a service plan selected by a customer, use ofconsumer devices may be tracked based on a number of RAN attachments,total RAN attachment duration, or other RAN connection parameters.

FIG. 1 is a diagram illustrating an exemplary network environment 100 inwhich systems and methods described herein may be implemented. Asillustrated, network environment 100 may include user equipment (UE)105, a radio access network (RAN) 110, a user plane function (UPF)device 115, a wireless core network 120, and a data network 190. Thedescriptions herein of network environment 100 generally referencesterminology and architecture from developing 3GPP 5G standards. However,other network standards and architectures may be used.

UE 105 may include a communication device (e.g., a mobile phone, a smartphone, a wearable computer device (e.g., a head-mounted display computerdevice, a wristwatch computer device, etc.), a global positioning system(GPS) device, and/or another type of wireless device); a laptopcomputer, a tablet computer, or another type of portable computer; amedia playing device; a portable gaming system; and/or any other type ofmobile computer device with communication and output capabilities.

In some implementations, UE 105 may correspond to an IoT device or anembedded wireless device that communicates wirelessly with other devicesover a machine-to-machine (M2M) interface. For example, UE 105 may beelectrically connected to any electronic device with a microcontroller,such as a microcontroller controlling one or more actuators, amicrocontroller controlling one or more sensors, a microcontroller thatperforms data processing, and/or another type of electronic device witha microcontroller. Non-limiting examples of such devices may include ahealth monitoring device (e.g., a blood pressure monitoring device, ablood glucose monitoring device, etc.), an asset tracking device (e.g.,a system monitoring the geographic location of a fleet of vehicles,etc.), a device controlling one or more functions of a vehicle (e.g., aclimate control system, an engine monitoring system, etc. smart homedevices (e.g., security cameras, sensors, thermostats, etc.) and/oranother type of electronic device. In some cases, UE 105 may be designedto perform a particular set of limited functions and, thus, may bereferred to as a resource constrained device.

According to an exemplary embodiment, UE 105 includes a communicationinterface via which UE 105 can transmit and receive data. According toan exemplary embodiment, the communication interface includes a wirelessmodem that supports broadband mobile communications with RAN 110. In a5G network architecture, UE 105 may connect to AMF device 125 via an NG1interface and to RAN 110 via an NR air interface.

RAN 110 includes one or multiple networks of one or multiple types toconnect UE 105 to components of network environment 100, includingconnections to UPF device 115 and AMF device 125. RAN 110 may be a 3rdGeneration (3G) RAN, a Fourth Generation (4G) RAN, a 4.5G RAN, a 5G RAN,a future generation wireless network architecture, etc. By way offurther example, access network 105 may include an Evolved UMTSTerrestrial Radio Access Network (E-UTRAN) of a Long Term Evolution(LTE) network or LTE-Advanced (LTE-A) network. Depending on theimplementation, access network 105 may include various network elements,such as a base station (BS), a Node B, an evolved Node B (eNB), a BScontroller, a radio network controller (RNC), a femto device, a picodevice, a home eNB, a relay node, a wireless access point, or other typeof wireless node that provides wireless access. RAN 110 may include awired network. For example, access network 105 may include an opticalnetwork or a cable network. RAN 110 may connect to UPF 115 via an NG3interface and to AMF device 125 via an NG2 interface. These and otherinterfaces described herein may be implemented using certain protocolssuch as, for example, a Diameter protocol.

UPF device 115 (also referred to simply as UPF 115) may include one ormore network elements to process user plane data. UPF 115 may connect toSMF device 130 via an NG4 interface and to data network 190 via an NG6interface.

Core network 120 may include network elements according to developing3GPP 5G network standards. Core network 120 may include, for example, anaccess and mobility management function (AMF) device 125, a sessionmanagement function (SW) device 130, a policy control function (PCF)device 140, an application function (AF) device 150, an authenticationserver function (AUSF) device 160, a unified data management (UDM)device 170. In addition, a usage-tracking (UT) server 180 may beincluded within or in communication with core network 120.

AMF device 125 (also referred to simply as AMF 125) may include one ormore network devices to provide common access control and mobilitymanagement (MM) functions for all accesses. AMF 125 maintains UE 105'sMM state, UE 105's mobility pattern and restriction policies, etc. AMF125 connects to SMF device 130 via an NG11 interface, to AUSF device 160via an NG12 interface, and to UDM 170 via an NG8 interface. As describedfurther herein, AMF 125 communicates with UT server 180 via a newtracking interface, referred to herein as an NG-RM interface. In oneimplementation, the NG-RM interface may be a dedicated interface forexchanging data and related controls between AN 125 and tracking server180.

SMF device 130 (also referred to simply as SMF 130) may include one ormore network devices to provide session management separate from MMfunctions of AMF 125. For example, SMF 130 collects data usage for UE105 sessions (e.g., with devices/applications in data network 190). SMF130 connects to PCF device 140 via an NG7 interface and to UDM 170 viaan NG10 interface. SMF may communicate with UT server 180 via an NG-CHinterface.

PCF device 140 (also referred to simply as PCF 140) may include one ormore network devices to provide policy control decision functionalities.PCF 140 may provide network control regarding service data flowdetection, gating, quality of service (QoS) and flow based charging,etc. PCF 140 may determine how a certain service data flow shall betreated, and may ensure that traffic mapping and treatment is inaccordance with a user's subscription profile. PCF 140 communicates withAMF 125 via an NG15 interface. SMF 130 via the NG7 interface, and AF 150via an NG5 interface.

AF device 150 (also referred to simply as AF 150) may include one ormore network devices to provide applications, data, and/or services toUE 105. In one example implementation, AF 150 may host a website fromwhich UE 105 can receive applications, data, and/or services. In anotherexample, AF 150 may be a content delivery server or providelocation-based services. AF 150 may communicate with PCF 140 via the NG5interface.

AUSF device 160 (also referred to simply as AUSF 160) may include one ormore network devices that manage permissions for UE 105. For example,AUSF 160 may verify that a UE 105 is authorized to access particulartypes of network services. AUSF 160 may communicate with AMF 125 via theNG12 interface and with UDM 170 via an NG13 interface.

UDM 170 may include one or more network devices that store user data.For example, UDM 170 may store subscription data, policy data (e.g., onquality of service and charging), and session related context (e.g., UE105 location), in a unified data layer. UDM 170 may communicate with AMF125 via the NG8 interface, with SMF 130 via the NG10 interface, and withAUSF via the NG13 interface.

UT server 180 may include one or more network devices. In oneimplementation, UT server 180 may provide a service plan code to AMF 125to allow AMF 125 to determine when (e.g., for which UE 105) to provideUE-RAN connection data (e.g., resource control (RRC) connection data orsimilar data). For each HE 105 under a RAN-usage-based plan, UT server180 may receive mobility management (MM) state data from AMF 125. In oneimplementation, UT server 180 may store control parameters for eachservice plan and track actual usage values (e.g., number of connections,duration of connections, MM state data, etc.) against the controlparameters. When a control parameter is exceeded, UT server 180 mayinitiate action to control/limit UE 105 connections to RAN 110 for aperiod of time. In another implementation, UT server 180 may log actualusage values to provide to a billing entity.

Data network 190 may include one or multiple networks of one or multipletypes. For example, data network 190 may be implemented as an IPnetwork, the Internet, an IMS network, a service or application-layernetwork, a proprietary network, a cloud network, a data network, etc.

In the example of FIG. 1, network elements and networks may be connectedby links using protocols for different interfaces interface NG1, NG2,etc.). A network element may transmit and receive data via a link.Environment 100 may be implemented to include wireless and/or wired(e.g., electrical, optical, etc.) links. A communicative connectionbetween network elements may be direct or indirect. For example, anindirect communicative connection may involve an intermediary device ornetwork element, and/or an intermediary network not illustrated inFIG. 1. Additionally, the number, the type (e.g., wired, wireless,etc.), and the arrangement of links illustrated in environment 100 areexemplary.

A network element may be implemented according to a centralizedcomputing architecture, a distributed computing architecture, or a cloudcomputing architecture (e.g., an elastic cloud, a private cloud, apublic cloud, etc.). Additionally, a network element may be implementedaccording to one or multiple network architectures client device, aserver device, a peer device, a proxy device, and/or a cloud device).

The number of network elements, the number of networks, and thearrangement in environment 100 are exemplary. According to otherembodiments, environment 100 may include additional network elements,fewer network elements, and/or differently arranged network elements,than those illustrated in FIG. 1. For example, there may be RAN 110,UPFs 115, AMFs 125, and so forth. Additionally, or alternatively,according to other embodiments, multiple network elements may beimplemented on a single device, and conversely, a network element may beimplemented on multiple devices. In other embodiments, one network inenvironment 100 may be combined with another network.

FIG. 2 is a diagram illustrating exemplary components of a device 200.Device 200 may correspond, for example, to a component of UE 105, UPF115, AMF 125, SMF 130, PCF 140, AF 150, AUSF 160, UDM 170, UT server180, or another component of network environment 100. Device 200 mayinclude a bus 210, a processor 220, a memory 230, an input component240, an output component 250, and a communication interface 260.

Bus 210 may include a path that permits communication among thecomponents of device 200. Processor 220 may include a processor, amicroprocessor, or processing logic that may interpret and executeinstructions. Memory 230 may include any type of dynamic storage devicethat may store information and instructions, for execution by processor220, and/or any type of non-volatile storage device that may storeinformation for use by processor 220. Input component 240 may include amechanism that permits a user to input information to device 200, suchas a keyboard, a keypad, a button, a switch, etc. Output component 250may include a mechanism that outputs information to the user, such as adisplay, a speaker, one or more light emitting diodes (LEDs), etc.

Communication interface 260 may include a transceiver that enablesdevice 200 to communicate with other devices and/or systems via wirelesscommunications, wired communications, or a combination of wireless andwired communications. For example, communication interface 260 mayinclude mechanisms for communicating with another device or system via anetwork. Communication interface 260 may include an antenna assembly fortransmission and/or reception of radio frequency (RF) signals. Forexample, communication interface 260 may include one or more antennas totransmit and/or receive RF signals over the air. Communication interface260 may, for example, receive RF signals and transmit them over the airto UE 105/RAN 110, and receive RF signals over the air from RAN 110/UE105. In one implementation, for example, communication interface 260 maycommunicate with a network and/or devices connected to a network.Alternatively or additionally, communication interface 260 may be alogical component that includes input and output ports, input and outputsystems, and/or other input and output components that facilitate thetransmission of data to other devices.

Device 200 may perform certain operations in response to processor 220executing software instructions contained in a computer-readable medium,such as memory 230. A computer-readable medium may be defined as anon-transitory memory device. A memory device may include space within asingle physical memory device or spread across multiple physical memorydevices. The software instructions may be read into memory 230 fromanother computer-readable medium or from another device. The softwareinstructions contained in memory 230 may cause processor 220 to performprocesses described herein. Alternatively, hardwired circuitry may beused in place of or in combination with software instructions toimplement processes described herein. Thus, implementations describedherein are not limited to any specific combination of hardware circuitryand software.

Device 200 may include fewer components, additional components,different components, and/or differently arranged components than thoseillustrated in FIG. 2. As an example, in some implementations, a displaymay not be included in device 200. In these situations, device 200 maybe a “headless” device that does not include input component 240.Additionally, or alternatively, one or more operations described asbeing performed by a particular component of device 200 may be performedby one or more other components, in addition to or instead of theparticular component of device 200.

FIG. 3 is a diagram illustrating exemplary logical components of AMF 125according to an implementation described herein. The functionalcomponents of AMF 125 may be implemented, for example, via processor 220executing instructions from memory 230 or via hardware. As shown in FIG.3, AMF 125 may include a radio resource data collector 310, a datareporting module 320, and an instruction module 330.

Radio resource data collector 310 may collect and update RAN access andmobility, status of UEs 105. For example, radio resource data collector310 may maintain a mobility management (MM) state for each UE 105. An MMstate may include an RM-deregistered state or an RM registered state,with the RM-registered state including a CM-idle state or a CM-connectedstate. Radio resource data collector 310 may also track non-accessstratum (NAS) signaling, such as a protocol data unit (PDU) request fromUE 105. Radio resource data collector 310 may further track mobilityrestrictions and mobility patterns for a UE 105.

Data reporting module 320 may report UE data/changes from radio resourcedata collector 310 to UT server 180 using, for example, the NG-RMinterface of FIG. 1. In one implementation, data reporting module 320may obtain from UDM 170 a service plan associated with UE 105. Forexample, UDM 170 may provide a UE service plan indicator to AMF 125whenever UE 105 requests permission to connect to RAN 110. The serviceplan indicator may direct a type of charging to be used for UE 105.Types of charging may include data-usage-based plans or RAN-usage-basedplans. When the service plan indicator for UE 105 indicates aRAN-usage-based plan, data reporting module 320 may provide UE 105'sRAN-usage parameters (as collected by radio resource data collector 310)to UT server 180 for support of radio connectivity-based,resource-based, or mobility-related charging and control. In oneimplementation, the RAN-usage parameters may be provided from AMF 125 toUT server 180 in real-time or near-real-time (e.g., within 500milliseconds). In another implementation, the RAN-usage parameters maybe provided from AMF 125 to UT server 180 as a batch process at timedintervals (e.g., up to one-minute intervals, etc.)

Instruction module 330 may receive control signals initiated by UTserver 180 to maintain UE 105 in conformance with a service plan, suchas a RAN-usage-based plan. For example, in one implementation,instruction module 330 may receive an indication that UE 105 hasexceeded a number of allotted RRC connections per day or another monitorMM state. In response, instruction module 330 may send a signal to UE105 (e.g., directly via interface NG1 or indirectly via interface NG2)to control/limit UE 105 signaling for the remainder of that day). Inanother implementation, instruction module 330 may send a signal toanother network element (e.g., RAN 110, AUSF 160) to enforce controls onUE 105 signaling in accordance with a service plan. In still anotherimplementation, instruction module 330 may enforce instructions,received from UT server 180, for compliance with a service plan for UE105.

Although FIG. 3 shows exemplary logical components of AMF 125, in otherimplementations, AMF 125 may include fewer logical components, differentlogical components, or additional logical components than depicted inFIG. 3. Additionally or alternatively, one or more logical components ofmay perform functions described as being performed by one or more otherlogical components.

FIG. 4A is a diagram illustrating exemplary logical components of UTserver 180 according to an implementation described herein. Thefunctional components of UT server 180 may be implemented, for example,via processor 220 executing instructions from memory 230. As shown inFIG. 4A, UT server 180 may include a data logging module 410, a chargingtable 420, and a reporting module 430.

Data logging module 410 may store s service plan information for each UE105 and log corresponding RAN-usage parameters received from datareporting module 320. In one implementation, data logging module may usecharging table 420 or another data structure to track that UE 105behavior is in accordance with an assigned service plan for the UE 105.

FIG. 4B provides a simplified example of charging table 420. As shown inFIG. 4B, charging table 420 may include a UE identifier (ID) field 421,a plan code field 422, a control parameter type field 423, a controlparameter value field 424, a charging log field 425, and a variety ofentries 426 associated with each of fields 421-425. Values for entries426 in fields 421-424 may be obtained by data logging module 410 fromsubscriber profile data, which may be provisioned directly to UT server180 or obtained from another network entity (e.g., UDM 170). Values forentries 426 in field 425 may be received from AMF 125 (e.g., via anNG-RM interface) and updated in real time.

UE ID field 421 may include a unique identifier for unique identifierfor a particular UE 105. For instance, UE ID field 421 may include amobile directory number (MDN), a mobile identification number (MIN), amobile equipment identity (MEID), an international mobile equipmentidentity (IMEI), an International Mobile Subscriber Identity (IMSI),etc.

Plan code field 422 may include a service plan code associated with theUE ID of field 421. For example, plan code field may include a serviceplan code obtained from a subscriber profile for UE 105. Plan code field422 may indicate, for example, a type of RAN-usage-based plan for UE105. In the simplified illustration of FIG. 4B, plan codes “R1-A” and“R1-B” may correspond to subscriber plans that allow a fixed number ofconnections per time period (e.g., for M2M-type reporting), plan code“R2” may correspond to a subscriber plan that allows a fixed number ofconnected minutes per time period, and plan code R3 may correspond to asubscriber plan that allo for transmission of a up to fixed number ofphysical resource blocks (PRBs) per time period.

Control parameter type 423 may include one or more parameterscorresponding to plan code field 422. For example, plan code “R1-A” mayindicate that a parameter for number of connections (e.g., RRCconnections) by UE 105 will be monitored. Similarly, plan code “R2” mayindicate that a parameter for a total connection time by UE 105 will bemonitored.

Control parameter value field 424 may include one or more parametervalues for a corresponding parameter type in plan code field 423. Forexample, plan code “R1-A” may be assigned a control parameter value of10 connections per day; plan code “R1-B” may be assigned a controlparameter value of unlimited connections per day; and plan code “R2” maybe assigned a control parameter value of 30 minutes per day. As show,for example, in connection with plan code “R3,” some plans may haveunlimited control parameter values (e.g., where charges accrued based ontotal use).

Charging log field 425 may include a dynamic count/total for UE 105corresponding to control parameter type field 423. Entries 426 incharging log field 425 may be updated based on data provided by AMF 125(e.g., data reporting module 320).

Returning collectively to FIGS. 4A and 4B, reporting module 430 maymonitor entries in charging table 420 and generate a report when acontrol parameter is exceeded for a UE 105. For example, reportingmodule 430 may report that UE 105 with UE ID “8914 0555 5555 5553” intable 420 has reached the daily 30-minute connection time limit forservice plan “R2.” in one implementation, reporting module 430 maygenerate a message (e.g., indicating an account limit has been reached)to be delivered to a subscriber/account holder. In anotherimplementation, reporting module 430 may generate a message to a networkentity, such as AMF 125 (e.g., instruction module 330), to control/limitactivity by the over-extended UE 105. Thus, reporting module 430 may usethe new NG-RM interface between AMF 125 and UT server 180 may passinstructions to AMF 125 for radio connectivity-based, resource-based, ormobility-related charging and control.

FIG. 5 is a signal flow diagram for logging radio resource use in aportion 500 of network environment 100. As shown in FIG. 5, networkportion 500 may include UE 105, RAN 110, AMF 125, UDM 170, and UT server180.

As shown in FIG. 5, at signal S501 UE 105 may provide a connectionrequest to RAN 110. A network device (e.g., a base station, eNode B, orthe like) in RAN 110 may receive the connection request and, at signalS502, may request authorization for UE 105 to attach to the network. AMF125 may conduct authentication and authorization procedures, which mayinclude forwarding an authorization request to UDM 170 at step S503, andobtaining subscription data from UDM 170 including a service plan codeat signal S504. The service plan code may indicate that the code is fora RAN-usage-based plan.

Assuming the service plan code indicates a RAN-usage-based plan for UE105, AMF 125 may receive the service plan code and identify that thecode is for a RAN-usage-based plan in signal S505. Based on theidentification, AMF 125 may begin reporting charging instances for UE105 to UT server 180 at signal S506. For example, AMF 125 may send to UTserver 180 indications of MM state changes for UE 105 (e.g., MMde-registers, AIM registered with idle state, MM registered withconnected state, etc.), NAS signaling by UE 105 (e.g., PDU requests), ormobility restrictions/mobility pattern data for UE 105. In oneimplementation, UT server 180 may receive the charging instances for UE105 and update an entry in a corresponding charging log field 425 ofcharging table 420.

FIGS. 6A and 6B are signal flow diagrams for controlling UE behaviorbased on radio resource use, according to implementations describedherein. Referring to FIG. 6A, a network portion 600 may include UE 105,RAN 110, AMF 125, and UT server 180. Signals for controlling UE behaviorbased on radio resource use may be transmitted through network portion600 using the NG-RM interface.

As shown in FIG. 6A, at signal S601 UT server 180 may identify that acontrol parameter is exceeded for a UE 105. For example, based on acomparison of entries for charging log field 425 and control parametervalue field 424, UT server 180 may determine that UE 105 has reach asubscription limit for RAN use (e.g., a number of daily connections, atotal connection time limit, etc.). Upon identifying that the controlparameter was exceeded, UT server 180 may report to AMF 125 (e.g., viathe NG-RM interface) that a control parameter has been exceeded atsignal S602. Additionally, or alternatively, UT server 180 may provideinstructions for controlling or limiting UE 105 behavior to conform tosubscription policies.

AMF 125 may receive the report/instructions from UT server 180 and, inresponse, may generate and/or forward control instructions to RAN 110via signal S603. RAN 110 may receive the control instructions. In oneimplementation, RAN 110 may implement the instructions to control/limitRAN activity by UE 105. In another implementation, RAN 110 may forwardthe instructions in signal S604 to LTE 105 for local implementation inaccordance with the subscriber's RAN-usage-based plan.

Referring to FIG. 6B, a network portion 610 may include UE 105, RAN 110,AMF 125, PCF 140, and UT server 180. In the example of FIG. 6B, signalsfor controlling UE behavior based on radio resource use may betransmitted through a network portion 610 without using the NG-RMinterface from UT server 180 to AMF 125. Similar to signal S601 of FIG.6A, signal S611 of FIG. 6B may identify that a control parameter isexceeded for a UE 105. Upon identifying that the control parameter wasexceeded, UT server 180 may report to PCF 140 (e.g., via interface NG15)that a control parameter has been exceeded at signal S612. Additionally,or alternatively, UT server 180 may provide instructions for controllingor limiting UE 105 behavior to conform to subscription policies. PCF 140may receive the report/instructions from UT server 180 and may forwardthe report/instructions to AMF 125 as signal S613.

AMF 125 may receive the report/instructions from PCF 140 and, inresponse, may generate and/or forward control instructions to RAN 110via signal S614. RAN 110 may receive the control instructions. RAN 110may implement the instructions to control/limit RAN activity by UE 105or forward the instructions in signal S615 to UE 105 for localimplementation in accordance with the subscriber's RAN-usage-based plan.

FIG. 7 is a flow diagram illustrating an exemplary process 700 fortracking charges based on radio resource utilization, according to animplementation described herein. In one implementation, process 700 maybe performed by AMF 125 and UT server 180. In another implementation,some or all of process 700 may be performed by another device or groupof devices in network environment 100.

As shown in FIG. 7, process 700 may include receiving a LIE connectionauthorization request from a RAN (block 710) and obtaining a plan codefor the UE (block 720). For example, as described in FIG. 5, UE 105 mayprovide a connection request to RAN 110. A network device (e.g., a basestation, eNode B, or the like) in RAN 110 may receive the connectionrequest and request authorization for UE 105 to attach to the network.AMF 125 may forward an authorization request to UDM 170 and obtainsubscription data from UDM 170 including a service plan code.

Process 700 may also include determining, based on the service plancode, if the UE requires RAN-usage-based tracking (block 730). Forexample, the plan code AMF 125 receives from UDM 170 may indicate thatUE 105 is using radio-connectivity-based charging.

If the UE requires RAN-usage-based tracking (block 730—Yes), process 700may include associating, based on the plan code, the UE with aRAN-usage-based plan (block 740) and sending, in response to theassociating, MM state changes by the UE to a tracking server device(block 750). For example, based on the plan code, AMF 125 may determinethat MM state change information for UE 105 must be forwarded to UTserver 180. In one implementation, indications of state changes may beprovided via the NG-RM interface between AMF 125 and UT server 180.

Process 700 may additionally include monitoring the HE trackinginstances against a control parameter (block 760) and identifying if acontrol parameter for the service plan code is exceeded (block 770). Forexample, for each HE 105 under a RAN-usage-based service plan, UT server180 may receive MM state data from AMF 125. UT server 180 may trackactual usage values received from AMF 125 (e.g., number of connections,duration of connections, etc.) against control parameters for acorresponding UE service plan. UT server 180 may determine when usage byUE 105 meets or exceeds a control parameter.

If a control parameter for the service plan code is exceeded (block770—Yes), process 700 may include generating control instructions forthe UE to control/limit RAN activity (block 780), and forwarding thecontrol instructions to the RAN (block 790). For example, when a controlparameter is exceeded, UT server 180 may initiate action tocontrol/limit UE 105 connections for a period of time. UT server 180 maysend control instructions to AMF 125, which may in turn forward aback-off timer value to UE 105 (either directly or via a base station inRAN 110) to limit future connection attempts within the controlledperiod.

Returning to block 730, if the UE does not require RAN-usage-basedtracking (block 730—No), process 700 may include not reporting trackinginstances of RAN usage by the UE to the usage-tracking server device(block 795). For example, if radio-connectivity-based tracking is notapplicable to UE 105, AMF 125 may not forward MM state data for UE 105to UT server 180. In such instances, tracking data may be collected andforwarded by other network elements in core network 120. For example,data usage amounts may be tracked by other network elements.

FIG. 8 is a diagram of a use case for controlling charges based on radioresource utilization, according to an implementation. With broadbandcellular communications, the radio network is typically the mostexpensive resource. Radio-connectivity-based tracking will allowoperators to offer subscription pricing based on radio resourceutilization. For example, connections and/or connection times logged byUT server 180 could simply be charged on a per-connection or per-minutebasis. However, radio-connectivity-based tracking will also provide away for operators to monitor and control UE 105 behavior by limiting theradio resource connection duration or by limiting the number of timesdevice is allowed to attach to a RAN per cycle (e.g., an hour, a day, aweek, etc.).

As described above, AMF 125 maintains UE's 105 MM status and terminatesNAS signaling with UE 105 directly via the NG1 interface. AMF 125interfaces with RAN 110 to setup a radio resource for UE 105 via the NG2interface. Radio-connectivity-based tracking may be implemented via theNG-RM interface between AMF 125 and UT server 180. Each time UE 105connects to RAN 110, AMF 125 may identify pricing structure for UE 105as radio-connectivity-based charging and report the connections to UTserver 180.

Assume in FIG. 8 that UE 105 is an IoT device with a service plan for 10RAN connections per day. Service plan information for UE 105 may beprovisioned to UT server 180, for example, when account for UE 105 iscreated with a service provider.

As shown in FIG. 8, UE 105 may request a tenth connection during thesame day (801), which would be permitted under the service plan for UE105. RAN 110 may provide a connection setup request to AMF 125 (802),AMF 125 may provide a connection indication to UT server 180 (803), andeventually the connection is authorized and serviced.

After the tenth attachment by UE 105 to RAN 110 within the same day, UTserver 180 may determine that UE 105 has reached the per-day connectionlimit (e.g., the control parameter) for the subscriber's service plan.For example, after receiving the tenth connection indication from AMF125, a comparison of control parameter value field 424 and charging logfield 425 in charging table 420 may show that UE 105 has reached a10-connection daily limit. UT server 180 may generate controlinstructions (804) to prevent additional connection attempts by UE 105during that day. In another implementation, UT server 180 may generatecontrol instructions in response to the first connection indicator thatexceeds the ten-connection parameter for UE 105.

In one implementation, the control instructions from UT server 180 mayinclude a back-off period (e.g., equal to the number of hours remainingin the day) for LTE 105. In another implementation, the controlinstructions from UT server 180 may provide instructions to AMF 125 orRAN 110 to determine the back-off period for UE 105. In any event AMF125 may provide back-off instructions to UE 105 to prevent additional“ping” request from UE 105 until the next day.

While FIG. 8 provides an example of subscription-based connectioncontrol based on a number of RAN connections, in other implementations,subscription-based connection controls may be based on connectiondurations (e.g. within a a day, week, month, etc.) by a UE 105 usingsimilar network communications.

In another implementation, the number of PRBs sent by UE 105 over aperiod may be used as a control parameter for radio-connectivity-basedcharging. The PRB is the minimum unit of radio resource allocation. Ascheduling function at a base station (e.g., eNode B) assigns the PRBsto carrier data and passes them to UE 105. RAN-resource-based chargingallows operators to charge customers based on the amount of PRBsconsumed during each session. Charging based on radio resource usageprovides finer granularity for operators to control the radio costs. RAN110 may report PRB usage to AMF 125 (e.g. via the NG2 interface).Similar to process described above, AMF 125 may forward the PRB data toUT server 180 for logging, monitoring, and managing.Radio-connectivity-based charging using PRBs may be well-suited for IoTdevices with fixed locations and low data usage.

According to implementations described herein, a method is provided forperforming RAN-usage-based tracking a wireless core network. The methodincludes receiving a connection authorization request from a radioaccess network (RAN); obtaining a service plan code for a communicationdevice associated with the connection authorization request;associating, based on the service plan code, the communication devicewith a RAN-usage-based plan; and sending, in response to theassociating, tracking instances of RAN usage by the communication deviceto a usage-tracking server device.

Adoption as an industry standard of the tracking interface andradio-connectivity-based charging described herein may enable wirelessservice providers to offer and enforce service plans for IoT devices andother characterized by sporadic data transmissions.

As set forth in this description and illustrated by the drawings,reference is made to “an exemplary embodiment,” “an embodiment,”“embodiments,” etc., which may include a particular feature, structureor characteristic in connection with an embodiment(s). However, the useof the phrase or term “an embodiment,” “embodiments,” etc., in variousplaces in the specification does not necessarily refer to allembodiments described, nor does it necessarily refer to the sameembodiment, nor are separate or alternative embodiments necessarilymutually exclusive of other embodiment(s). The same applies to the term“implementation,” “implementations,” etc.

The foregoing description of embodiments provides illustration, but isnot intended to be exhaustive or to limit the embodiments to the preciseform disclosed. Accordingly, modifications to the embodiments describedherein may be possible. For example, various modifications and changesmay be made thereto; and additional embodiments may be implemented,without departing from the broader scope of the invention as set forthin the claims that follow. The description and drawings are accordinglyto be regarded as illustrative rather than restrictive.

The terms “a,” “an,” and “the” are intended to be interpreted to includeone or more items. Further, the phrase “based on” is intended to beinterpreted as “based, at least in part, on,” unless explicitly statedotherwise. The term “and/or” is intended to be interpreted to includeany and all combinations of one or more of the associated items. Theword “exemplary” is used herein to mean “serving as an example.” Anyembodiment or implementation described as “exemplary” is not necessarilyto be construed as preferred or advantageous over other embodiments orimplementations.

In addition, while a series of blocks has been described with regard tothe process illustrated in FIG. 7, the order of the blocks may bemodified according to other embodiments. Further, non-dependent blocksmay be performed in parallel. Additionally, other processes described inthis description may be modified and/or non-dependent operations may beperformed in parallel.

The embodiments described herein may be implemented in many differentforms of software executed by hardware. For example, a process or afunction may be implemented as “logic,” a “component,” or an “element.”The logic, the component, or the element, may include, for example,hardware (such as a processor, an ASIC, or a FPGA) or a combination ofhardware and software. The embodiments have been described withoutreference to the specific software code since the software code can bedesigned to implement the embodiments based on the description hereinand commercially available software design environments and/orlanguages.

Use of ordinal terms such as “first,” “second,” “third,” etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another, thetemporal order in which acts of a method are performed, the temporalorder in which instructions executed by a device are performed, etc.,but are used merely as labels to distinguish one claim element having acertain name from another element having a same name (but for use of theordinal term) to distinguish the claim elements.

To the extent the aforementioned embodiments collect, store or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the invention unless explicitlydescribed as such.

What is claimed is:
 1. A method, comprising: receiving, by a networkdevice in a wireless core network, a connection authorization requestfrom a radio access network (RAN); obtaining, by the network device, aplan code for a communication device associated with the connectionauthorization request; associating, by the network device and based onthe plan code, the communication device with a RAN-usage-based plan; andsending, by the network device and in response to the associating,tracking instances of RAN usage by the communication device to ausage-tracking server device.
 2. The method of claim 1, furthercomprising: monitoring, by the usage-tracking server device, thecommunication device tracking instances against a control parameter forthe RAN-usage-based plan associated with the plan code; and identifying,by the usage-tracking server device, that the tracking instances exceedthe control parameter.
 3. The method of claim 2, wherein the controlparameter includes one of: a designated number of connections to the RANby the communication device within a time period, or a duration ofconnection time to the RAN by the communication device within the timeperiod.
 4. The method of claim 2, further comprising: generating, by oneof the network device or the usage-tracking server, control instructionsfor the communication device to limit RAN activity in response toidentifying that the tracking instances exceed the control parameter. 5.The method of claim 4, wherein the control instructions for thecommunication device to control/limit RAN activity include: instructionsto block the communication device from establishing a connection withthe RAN until a back-off timer expires.
 6. The method of claim 1,wherein sending the tracking instances of RAN usage includes sending thetracking instance in real time or near-real time.
 7. The method of claim1, wherein sending the tracking instances of RAN usage includesreporting the tracking instances via a dedicated tracking interfacebetween the network device and the usage-tracking server device.
 8. Themethod of claim 1, wherein the network device is an access and mobilitymanagement function (AMF) in the wireless core network.
 9. The method ofclaim 1, wherein the tracking instances include change in a mobilitymanagement (MM) state for the communication device.
 10. The method ofclaim 1, further comprising: receiving, by the network device, anotherconnection authorization request from the RAN; obtaining, by the networkdevice, another plan code for a different communication deviceassociated with the other connection authorization request; and notreporting, by the network device, tracking instances of RAN usage by thedifferent communication device to the usage-tracking server device. 11.A system, comprising: a network device for a wireless core network, thenetwork device including a first memory and a first processor to executeinstructions in the first memory to: receive a connection authorizationrequest from a radio access network (RAN); obtain a plan code for acommunication device associated with the connection authorizationrequest; associate, based on the plan code, the communication devicewith a RAN-usage-based plan; and send, in response to the associating,tracking instances of RAN usage by the communication device to ausage-tracking server device.
 12. The system of claim 11, wherein thefirst processor is further to execute instructions in the first memoryto: forward control instructions for the communication device to limitRAN activity when the tracking instances exceed a control parameter forthe RAN-usage-based plan associated with the plan code.
 13. The systemof claim 11, further comprising: the usage-tracking server device forthe wireless core network, the usage-tracking server device including asecond memory and a second processor to execute instructions in thesecond memory to: monitor the communication device tracking instancesagainst a control parameter for the RAN-usage-based plan associated withthe plan code; and identify that the tracking instances exceed thecontrol parameter.
 14. The system of claim 13, wherein the controlparameter includes one of: a designated number of connections to the RANby the communication device within a time period, or a duration ofconnection time to the RAN by the communication device within the timeperiod.
 15. The system of claim 13, wherein the second processor isfurther to execute instructions in the second memory to: generatecontrol instructions for the communication device to limit RAN activityin response to identifying that the tracking instances exceed thecontrol parameter.
 16. The system of claim 11, wherein, when sending thetracking instances of RAN usage by the communication device to theusage-tracking server device, the first processor is further to: use adedicated interface between the network device and the usage-trackingserver device.
 17. A non-transitory co pr er-readable medium storinginstructions executable by a computational device to: receive aconnection authorization request from a radio access network (RAN);obtain a plan code for a communication device associated with theconnection authorization request; associate, based on the plan code, thecommunication device with a RAN-usage-based plan; and send, in responseto the associating, tracking instances of RAN usage by the communicationdevice to a usage-tracking server device.
 18. The non-transitorycomputer-readable medium of claim 7, further comprising instructions to:forward control instructions for the communication device to limit RANactivity when the tracking instances exceed a control parameter for theRAN-usage-based plan associated with the plan code.
 19. Thenon-transitory computer-readable medium of claim 17, wherein theinstructions to send the tracking instances of RAN usage includessending the tracking instance in real time via a dedicated interface.20. The non-transitory computer-readable medium of claim 19, wherein thenon-transitory computer-readable medium is included within an access andmobility management function (AMF) of a wireless core network.